Skip to content

feat(flutter_package): added post_setup_command in flutter_package workflow - #461

Open
dev-gyata wants to merge 1 commit into
VeryGoodOpenSource:mainfrom
dev-gyata:main
Open

feat(flutter_package): added post_setup_command in flutter_package workflow#461
dev-gyata wants to merge 1 commit into
VeryGoodOpenSource:mainfrom
dev-gyata:main

Conversation

@dev-gyata

@dev-gyata dev-gyata commented Jul 7, 2026

Copy link
Copy Markdown

Status

READY

Description

Adds a new optional post_setup_command input to the flutter_package GitHub Actions workflow. This command runs after the existing setup step and before formatting, analysis, linting, and tests, allowing callers to perform extra specific preparation without modifying the shared workflow.

Example usage:

post_setup_command: |
  flutter pub run build_runner build --delete-conflicting-outputs

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@dev-gyata
dev-gyata requested a review from a team as a code owner July 7, 2026 15:21
@dev-gyata dev-gyata changed the title feat(ci): added post_setup_command in flutter_package workflow feat(flutter_package): added post_setup_command in flutter_package workflow Jul 30, 2026
@marcossevilla

Copy link
Copy Markdown
Member

hi @dev-gyata, thanks for opening a PR!

I'd think this same behavior can be achieved adding the build_runner command in the setup step, right? not sure if you already tried it but if you did, let me know if you had any issues 👍

@marcossevilla marcossevilla added the waiting for response Waiting for follow up label Aug 10, 2026
@marcossevilla marcossevilla self-assigned this Aug 10, 2026
@dev-gyata

dev-gyata commented Aug 10, 2026

Copy link
Copy Markdown
Author

Hi @marcossevilla I never know this but then the build runner i used was just an example. it could be a different command

@marcossevilla

Copy link
Copy Markdown
Member

@dev-gyata yeah I mean, the setup step can receive multiple commands if you make it multiline, so in that case you can add any commands you need before linting, formatting, testing, etc.

adding a post_setup_command feels redundant since you can just add that command to the setup step, but I'm not sure if you had any problems doing so?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting for response Waiting for follow up

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants